Skip to content

Conversation

natebosch
Copy link
Member

There are definitions in test_core which override the _declarer to
work even when the test script is run directly instead of through the
test runner. The definitions from test_api should not be used anywhere
currently.

natebosch added 3 commits June 5, 2023 17:37
There are definitions in `test_core` which override the `_declarer` to
work even when the test script is run directly instead of through the
test runner. The definitions from `test_api` should not be used anywhere
currently.
Add an override on `matcher` for `test_api` for breaking version change.
@natebosch
Copy link
Member Author

This is currently incompatible with flutter_test which uses a hide for these members. If we change that to a show listing the stuff that will stay it should work better.

@natebosch natebosch added the next-breaking-release Issues that are worth doing but need to wait for a breaking version bump label Jun 5, 2023
natebosch added a commit to natebosch/flutter that referenced this pull request Jun 5, 2023
The members which are currently hidden may get removed from
`package:test_api` because they have no uses.
dart-lang/test#2030

Switch to a `show` and list all the exported APIs. This is currently a
no-op change, and is forward compatible with the breaking change when it
lands.

A `show` is also safer than a `hide` when exporting across package
boundaries. Adding a new member to a library _can be_ breaking, but is
often treated as non-breaking. If a new member is added to
`package:test_api/scaffolding.dart` it will need to be manually added to
the list to be usable from `package:flutter_test`, but we anyways want
to add a CHANGELOG entry for user facing changes.
auto-submit bot pushed a commit to flutter/flutter that referenced this pull request Jun 6, 2023
The members which are currently hidden may get removed from `package:test_api` because they have no uses.
dart-lang/test#2030

Switch to a `show` and list all the exported APIs. This is currently a no-op change, and is forward compatible with the breaking change when it lands.

A `show` is also safer than a `hide` when exporting across package boundaries. Adding a new member to a library _can be_ breaking, but is often treated as non-breaking. If a new member is added to `package:test_api/scaffolding.dart` it will need to be manually added to the list to be usable from `package:flutter_test`, but we anyways want to add a CHANGELOG entry for user facing changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
next-breaking-release Issues that are worth doing but need to wait for a breaking version bump
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant